home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 6
/
The Arsenal Files 6 (Arsenal Computer).ISO
/
doorware
/
lisa18.zip
/
HELP.TXT
< prev
next >
Wrap
Text File
|
1996-03-15
|
8KB
|
171 lines
The following text describes problems and solutions that have been
encountered when installing Lisa. Some of the information is provided
courtesy of T&J Software. They are not related to ChAoS Online or to
Chat With Lisa, but they do use the same DoorFrame software as Lisa.
MY REGISTRATION CODE DOESN'T WORK
=================================
* The #1 reason for not working: The names in the LISA.CFG file do not
match the names (spelling) on your registration form. If you registered
by mail, double-check the BBS name and the SYSOP name on the form we
sent you. If you registered online, call ChAoS and double-check the
names by selecting "Display Door Code" from the Purchase Menu.
* Other reasons the code might not work: The code entered in LISA.CFG was
typed wrong or has spaces in it; or LISA.CFG was renamed. (see below).
THE SETTINGS IN MY CONFIG FILE HAVE NO EFFECT
=============================================
* Lisa always gets her settings from the LISA.CFG file. Did you change
the name or create multiple .CFG files? Change the filename back to
LISA.CFG and edit the settings there. If your BBS has multiple nodes,
read the MULTIPLE NODES section of the SYSOP.TXT file.
THE LOCAL SCREEN DISPLAY IS GARBAGE
===================================
* This is almost always caused by ANSI not being installed. You need
to add the following line to your CONFIG.SYS file:
DEVICE=C:\DOS\ANSI.SYS
Reboot the machine after adding the line. Read your DOS manual
for more information about the ANSI.SYS screen driver.
* If you are multi-tasking with DesqView, do the following instead:
Add DVANSI.COM to the batch file for each node.
LOCKUPS ON CERTAIN COM PORTS or GARBLED INFORMATION ON REMOTE
=============================================================
* If the remote terminal cannot receive, or the screen is garbled,
you are probably using a non-standard IRQ. Make sure you are
passing the correct IRQ value to the door in the batch file.
Example: LISA LISA.CFG /5
* If you are using a multi-port board with a fossil driver, use
the following: LISA LISA.CFG /FD
Please read SYSOP.TXT for complete information.
DOOR.SYS PROBLEMS or `OUT OF STRING SPACE' ERRORS
=================================================
* Problems may develop when using the DOOR.SYS drop file if you have
a large number of conferences. Due to the specifications of DOOR.SYS,
all the conferences that a user is "joined to" are written to line
#23 of DOOR.SYS. This may cause the DOOR.SYS file to become too large,
which usually results in the "out of string space" error.
* WildCat 4.0 users should download a file called FDOORSYS.ZIP written
by Tim Rider (call The Source BBS at 310-371-3737). This small utility
will remove the offending line in DOOR.SYS.
* Wildcat 4.01+ users can go to the MakeWild Doors Menu and change the
door setup to use a "small" DOOR.SYS drop file.
* PCBoard users should use the PCBOARD.SYS drop file.
KEYBOARD TIMEOUTS AND 486DX COMPUTERS
=====================================
* If you are using a 486DX computer and keep getting "keyboard timeout"
errors, or ERROR 5 or 6, you need to place the following line in your
AUTOEXEC.BAT file:
SET NO87=ON
This will turn off your math co-processor and allow the door to
function properly.
OVERFLOW ERRORS
===============
* Overflows can occur if you are running under DesqView and your tick
counts are set too low -- try raising the tick counts.
* If you're running Wildcat! v3.9+ and are getting OVERFLOW errors,
make sure NONE of your security level definitions have the MAXIMUM
DAILY DOWNLOADS set to more than 32,000 -- anything over that will
cause an OVERFLOW ERROR in any door using DOORFRAME.
GRAPHIC CARDS (general)
=======================
* ATI Graphics Ultra Pro card - do not use the ANSI.SYS driver that
came with the card. Use the normal DOS ANSI.SYS for the screens
to show correctly.
* Trident SVGA Cards - You should have a utility disk with a file
called TANSI.SYS, use this ansi driver instead of DOS ANSI.SYS.
DESQVIEW/X
==========
* Make sure you have the MATH COPROCESSOR flagged ON even if you
don't have a math coprocessor.
REMOTE ACCESS v2.0+
===================
* Using DOOR.SYS may result in an OVERFLOW error -- try using a
different caller drop file such as DORINFO1.DEF. This is currently
being examined!
RENEGADE BBS
============
* If you are using the BNU fossil driver and having problems with doors,
try using X00 v1.50+. Several Renegade systems have reported problems
using BNU with doors.
* If you are getting out-of-memory errors, go into the System Config
section, [E] System Toggles, then [U] to turn the SWAP FILE 'ON'.
SPITFIRE BBS's
==============
* If you're having trouble with the door dropping carrier on exiting
back to the BBS, switch to using DOOR.SYS instead of SFDOORS.DAT.
This happens on some Spitfire configurations when using SFDOORS.DAT.
TRIBBS v5.02+
=============
* Color ANSI checking will not work if you use TRIBBS.SYS drop file.
Set the doors up using the PCBOARD.SYS drop file.
* If you use DOOR.SYS, TriBBS reloads this file and will deduct twice
the amount of time that was actually used. Try using another drop
file, or copying the DOOR.SYS to a separate directory and then
telling the door to look there for it.
* NOTE: This only applies to doors where you adjust the user's time
in the door such as Bordello, Studs, and Studette.
WILDCAT! 3.X
============
* You must use the caller drop file DOOR.SYS to make sure the callers
remaining time is passed back to Wildcat.
* Wildcat! IM Version Setup using DigiFossil v2.x:
All T&J doors will run on the Wildcat! IM version using DigiFossil
v2.x. I have received TWO different setup routines concerning the
IM version, here's an example:
DF LOCK%WCNODEID% -OR- DF ON
CD\DOORS\GAME CD\DOORS\GAME
GAME GAME.CFG /FD GAME GAME.CFG
CD\WC30 CD\WC30
DF OFF DF OFF
SOME QUICKBASIC ERROR CODES (DOORFRAME USES THE SAME CODES)
===========================================================
2 Syntax error 61 Disk full
5 Illegal function call 62 Input past end of file
6 Overflow 63 Bad record number
7 Out of memory 64 Bad filename
11 Division by zero 67 Too many files
13 Type mismatch 68 Device unavailable
24 Device timeout 69 Comm-buffer overflow
25 Device fault 70 Permission denied
52 Bad filename or number 71 Disk not ready
53 File not found 72 Disk media error
55 File already open 74 Rename across disk
57 Device I/O error 75 Path/File access error
58 File already exists 76 Path not found
59 Bad record length
Error #53 can be caused by a missing LISA.CFG or LISA.DAT file, or the
program cannot find the BBS drop file. Error #62 is usually caused by
the LISA.CFG file not having enough lines. Error #75/76 usually results
from an incorrect path and/or filename in line 1 of the LISA.CFG file.